Skip to content

Conversation

@Donaim
Copy link
Member

@Donaim Donaim commented Dec 23, 2025

No description provided.

@Donaim Donaim force-pushed the integrate-exact-coverage branch from d36fc78 to 9281401 Compare December 23, 2025 20:42
@codecov
Copy link

codecov bot commented Dec 23, 2025

Codecov Report

❌ Patch coverage is 6.06061% with 31 lines in your changes missing coverage. Please review.
✅ Project coverage is 85.94%. Comparing base (7504784) to head (bd1b30d).
⚠️ Report is 4 commits behind head on master.

Files with missing lines Patch % Lines
micall/core/aln2counts.py 6.06% 31 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1470      +/-   ##
==========================================
- Coverage   86.30%   85.94%   -0.37%     
==========================================
  Files          29       29              
  Lines        7297     7330      +33     
==========================================
+ Hits         6298     6300       +2     
- Misses        999     1030      +31     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Donaim Donaim force-pushed the integrate-exact-coverage branch from 4bcad8b to 72fed9d Compare December 23, 2025 22:36
A simple, semantically invariant, change that optimizes variables lookup.
The offset field only indicates where the original alignment placed the read.
Exact coverage does its own k-mer based matching independent of the alignment position.
A read with offset=5 can (and should) still contribute exact coverage data wherever it matches exactly in the reference.
The filter was unnecessarily discarding valid coverage information.
@Donaim Donaim closed this Jan 5, 2026
@Donaim Donaim deleted the integrate-exact-coverage branch January 5, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants